1. Release History

November 30, 2006

LDAP v6.0.3.5 is released.

Changes:

Fixed: Log in to Windows as a user who cannot be automatically logged into the client. Request <your hostname>/login. The user ends up with the HTTP Bad Request error.

August 22, 2006

LDAP v6.0.3.4 is released.

Changes:

Fixed: Users or Groups with a dash ('–') in their name in your directory cannot be replicated into Sitecore.

May 04, 2006

LDAP version 6.0.3.3 is released.

Changes:

Fixed: Extranet user is unable to login directly when language of the site is other than English.

April 03, 2006

LDAP version 6.0.3.2 is released.

Changes:

Fixed: issue concerning names with comma
Fixed: search fails after the language attribute in the modules_shell site is set to any other than "en"

February 28, 2006

LDAP version 6.0.3.1 is released.

Changes:

License Agreement is updated

February 10, 2006

LDAP version 6.0.3 is released.

Changes:

The module runs on Sitecore v5.1.1
The issue with invalid names has been fixed.
Documentation is updated.
A task Item which initiates an update of the LDAP Client and Extranet security in Sitecore has been added to the module’s main window.
The problem with adding custom fields to a User or a group has been fixed.
The ‘Require Directory Membership’ option has been removed.

October 21, 2005

LDAP version 6.0.2 is released.

2. Known Issues

When you add a group using the LDAPmodule, the following will be written in the log - 3404 16:34:15 WARN The path "/sitecore/system/languages" was not found.
Warning entries appear in the Log file when you add a User or a group with LDAP application. For instance:
5532 18:24:44 WARN Could not resolve security item (AKLDAPgroup). Key: akldapgroup{A7DF04B4-4C4B-44B7-BE1E-AD901BD53DAD}
5532 18:24:44 WARN Could not resolve security item (alko). Key: alko{642C9A7E-EE31-4979-86F0-39F338C10AFB}
It’s not possible for an added User that has the “Password must be changed at next logon” option set in your directory to login to Sitecore (this only concerns the Live Validation and Mixed modes).
v6.0.0 issue: In the Mixed mode, the module allows an added User to login only if one of the groups, which he belongs to, is already added. Otherwise, an empty page with an error string appears.
Currently, the module comes in the English language version only.
The Send Mail functionality doesn't work in the Mixed mode in LDAP Module v6.0.2.
The Full name radio button can be selected, but appears as disabled.
The Add Groupsmembers setting (System » Modules » LDAP » LDAPclient/extranet) duplicates the Add Groupmembers checkbox in LDAP application.
After successful or unsuccessful login to Sitecore via the <your hostname>/Sitecore link, added groups cannot be deleted from Sitecore security by LDAP module.
If you change the mode from "Live" to "Mixed", you must delete all ldap temporary users from the sitecore/users/temporary folder in Sitecore and Extranet databases.

3. Limitations

The module cannot register user primary groups in Active Directory.
It is required that your directory users contains a property informing which group the User is a member of – is default in AD and eDir; however, it can be a problem if you’re running in a Notes/Domino environment.
When a User tries to login to Sitecore, only valid direct memberships are registered, not the transitive (nested) ones.
The update for added fields works properly only if the LDAP field name, the value of the field’s Title property and the name of the field in the Security templates.xml file are identical.